Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README with Documentation roadmap #296

Open
wants to merge 1 commit into
base: trunk
Choose a base branch
from
Open

Update README with Documentation roadmap #296

wants to merge 1 commit into from

Conversation

imath
Copy link
Contributor

@imath imath commented Sep 17, 2024

@emaralive @vapvarun @dcavins @renatonascalves

As discussed during September 4 docs chat, here's the PR we can improve to explain our goals/roadmap about BuddyPress documentation.

@emaralive
Copy link
Collaborator

emaralive commented Sep 18, 2024

I think we should archive the current master as a branch, prior to merging this pull request, this allows for an easy method to see/retain the 1st (original) version, if you will.

With this pull request we can then:

  • Remove the data folder & it's content, since we would have an archive branch that has this info, in the event we need to reference anything from that content.
  • Remove 1-migrate-task.yml from the .github/ISSUE_TEMPLATE folder since it is now obsolete and will exist in the archive branch.
  • Remove 3-ignore-task.yml from the .github/ISSUE_TEMPLATE folder since it is now obsolete and will exist in the archive branch.
  • Rename 2-add-task.yml to 1-add-task.yml, keeping a similar numeric prefix.
  • Rename 4-update-task.yml to 2-update-task.yml, keeping a similar numeric prefix.
  • Create a folder named roadmap, which will contain any detailed info that further describes/defines the top-level roadmap (as spelled out by the final version of the README.md), e.g., there would be links from the roadmap (README.md to whatever detailed .md files that are created).

Or, someone else can come up with a better idea and we can do that or stick with the PR as originally submitted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants